Use tmpdir within /data for barman-cloud-backup/-restore#300
Use tmpdir within /data for barman-cloud-backup/-restore#300dangra merged 1 commit intofly-apps:masterfrom
Conversation
|
hey @immerrr, I am fine with the wrapper script. The PR needs a rebase, thanks for the pg17 and haproxy fixes btw. |
|
different situation but having same trouble: since the root disk is only 8GB and here's the entire logs of barman-cloud-backup the annoying thing is, postgres user tried to re-run so we needed to run barman-cloud-backup with different user like this: and kill tmp file periodically, to avoid disk full ps. I found we can change rootfs size; will try this when I encounter this issue again |
|
Hi @dangra , do we have a plan to merge this PR? since our unmanaged psql has 50GB and unable to generate backup due to this issue, it'd be nice if you could merge this |
1cf71f1 to
53be32d
Compare
We are having an issue with postgres backups created by barman: they are failing, because barman creates a tar archive in
/tmpdirectory, which only has ~7.5G to work with, so it runs out of space.I've checked barman sources, and it didn't seem to have a way to configure its temp. directories, so I ended up making a wrapper script that creates a temporary directory in a place of your choice, and configured
barman-cloud-backupandbarman-cloud-restorecommands to run through that script.There should be a better way to handle this, but I wanted to get some early opinions on this.
Also, had to fix the haproxy configs, it seemed to complain about having two
server-templateclauses with the same namepg